Vulnmap Language Server (Vulnmap-LS)

Supported features

The language server follows the Language Server Protocol and integrates with Vulnmap Open Source, Vulnmap Infrastructure as Code and Vulnmap Code. For the former two, it uses the Vulnmap CLI as a data provider, for the latter it is connecting directly to the Vulnmap Code API.

Right now the language server supports the following actions:

• Send diagnostics to client on opening a document if it's part of the current set of folders.
• Starting a folder scan on startup and sending diagnostics.
• Starting a workspace scan of all folders on command.
• Cache diagnostics until saving or triggering a new workspace scan.
• Invalidate caches on saving a document and retrieve saved document diagnostics anew.
• Provides range calculation to correctly highlight Vulnmap Open Source issues in their file.
• Provides formatted hovers with diagnostic details and follow-up links
• Progress reporting to the client for background jobs
• Notifications & Log messages to the client
• Authentication when needed, using OAuth2 or Token authentication and opening a webpage if necessary
• Copying the authentication URL to clipboard if there are problems opening a webpage
• Automatic download of the Vulnmap CLI if none is found or configured to XDG_DATA_HOME
• Selective activation of products according to settings transmitted
• Scanning errors are reported as diagnostics to the Language Server Client
• Code Lenses to navigate the Vulnmap Code dataflow from within the editor
• Code Actions for in-editor commands, like opening a browser, doing a quickfix or opening a Vulnmap Learn lesson for the found diagnostic

Implemented operations

Language Server Protocol support

Requests

• initialize
• exit
• textDocument/codeAction
• textDocument/codeLens
• textDocument/didClose
• textDocument/didSave
• textDocument/hover
• textDocument/inlineValue
• shutdown
• workspace/didChangeWorkspaceFolders
• workspace/didChangeConfiguration
• workspace/executeCommand
• window/workDoneProgress/create (from server -> client)
• window/showMessageRequest
• window/showDocument

Notifications

• $/progress
• textDocument/publishDiagnostics
• window/logMessage
• window/showMessage

Custom additions to Language Server Protocol

• Authentication Notification

  • method: $/vulnmap.hasAuthenticated
  • payload:

  {
    "token": "the vulnmap token" // this can be an oauth2.Token string or a legacy token
  }

  • See https://pkg.go.dev/golang.org/x/oauth2@v0.6.0#Token for more details regarding oauth tokens.

• Cli Path Notification

  • method: $/vulnmap.isAvailableCli
  • payload:

  {
    "cliPath": "/a/path/to/cli-executable"
  }

• Trust Notification

  • method: $/vulnmap.addTrustedFolders
  • payload:

  {
    "trustedFolders": ["/a/path/to/trust"]
  }

• Scan Notification

  • method: $/vulnmap.scan
  • payload:

  {
    "status": "inProgress", // possible values: "error", "inProgress", "success"
    "product": "code", // possible values: "code", "oss", "iac"
    "results" : [
      // TBD
    ]
  }

Commands

• NavigateToRangeCommand navigates the client to the given range
  • command: vulnmap.navigateToRange
  • args: path, Range
• WorkspaceScanCommand triggers a scan of all workspace folders
  • command: vulnmap.workspace.scan
  • args: empty
• WorkspaceFolderScanCommand triggers a scan of the given workspace folder
  • command: vulnmap.workspaceFolder.scan
  • args: path
• OpenBrowserCommand opens the given URL in the default browser
  • command: vulnmap.openBrowser
  • args: URL
• LoginCommand triggers the login process
  • command: vulnmap.login
  • args: empty
• CopyAuthLinkCommand copies the authentication URL to the clipboard
  • command: vulnmap.copyAuthLink
  • args: empty
• LogoutCommand triggers the logout process
  • command: vulnmap.logout
  • args: empty
• TrustWorkspaceFoldersCommand checks for trusted workspace folders and asks for trust if necessary
  • command: vulnmap.trustWorkspaceFolders
  • args: empty
• OpenLearnLesson opens the given lesson on the Vulnmap Learn website
  • command: vulnmap.openLearnLesson
  • args:
    • rule string
    • ecosystem string
    • cwes string (comma separated), e.g. CWE-79,CWE-89
    • cves string (comma separated), e.g. CVE-2018-11776,CVE-2018-11784
    • issueType int

    PackageHealth Type = 0
    CodeQualityIssue = 1
    CodeSecurityVulnerability = 2
    LicenceIssue = 3
    DependencyVulnerability = 4
    InfrastructureIssue = 5
    ContainerVulnerability = 6
    

• GetLearnSession returns the given lesson on the Vulnmap Learn website
  • command: vulnmap.getLearnLesson
  • args:
    • rule string
    • ecosystem string
    • cwes string (comma separated), e.g. CWE-79,CWE-89
    • cves string (comma separated), e.g. CVE-2018-11776,CVE-2018-11784
    • issueType int

    PackageHealth Type = 0
    CodeQualityIssue = 1
    CodeSecurityVulnerability = 2
    LicenceIssue = 3
    DependencyVulnerability = 4
    InfrastructureIssue = 5
    ContainerVulnerability = 6
    

  • result: lesson json

  {
  "lessonId": "123",
  "datePublished": "2022-01-01",
  "author": "John Doe",
  "title": "Introduction to Golang",
  "subtitle": "A beginner's guide to Golang",
  "seoKeywords": ["Golang", "Programming", "Beginner"],
  "seoTitle": "Learn Golang",
  "cves": ["CVE-2022-1234", "CVE-2022-5678"],
  "cwes": ["CWE-123", "CWE-456"],
  "description": "This lesson provides an introduction to Golang for beginners",
  "ecosystem": "Programming",
  "rules": ["Rule 1", "Rule 2", "Rule 3"],
  "slug": "golang-intro",
  "published": true,
  "url": "https://example.com/golang-intro",
  "source": "Example.com",
  "img": "https://example.com/images/golang-intro.png"
  }

• SettingsSastEnabled triggers the api call to check if Vulnmap Code is enabled
  • command: vulnmap.settingsSastEnabled
  • args: empty
  • returns true if enabled, false if not, or an error and false if an error occurred
• GetActiveUser triggers the api call to get the active logged in user or an error if not logged in
  • command: vulnmap.getActiveUser
  • args: empty
  • returns the active user and its orgs and groups or an error if not logged in.

  {
    "id": "123",
    "username": "johndoe",
    "orgs": [
     {
       "name": "org1",
       "id": "org1_id",
       "group": {
          "name": "group1",
          "id": "group1_id"
       }
     }
    ],
  }

Installation

Download

The release workflow stores the generated executables, so that they can be downloaded here. Just select the release you want the build artefacts from and download the zip file attached to it. Currently, executables for Windows, macOS and Linux are generated.

The currently published binary can be retrieved with this bash script, please keep in mind that the protocol version is part of the download link and can change to force plugin / language server synchronization. For further information please see CONTRIBUTING.md.

From Source

• Install go 1.20 or higher, set the GOPATH and GOROOT
• Enter the root directory of this repository
• Execute go get ./... to download all dependencies
• Execute make build && make install to produce a vulnmap-ls binary

Configuration

Vulnmap LSP Command Line Flags

-c <FILE> allows to specify a config file to load before all others

-f <FILE> allows you to specify a log file instead of logging to the console

-l <LOGLEVEL> <allows to specify the log level (trace, debug, info, warn, error, fatal). The default log level is info. This can be overruled by setting the env variable VULNMAP_DEBUG_LEVEL, e.g. export VULNMAP_DEBUG_LEVEL=debug

-licenses (running standalone) displays the licenses used by Language Server
--licenses (running within Vulnmap CLI)

-o <FORMAT> allows to specify the output format (md or html) for issues

-v prints the version of the Language Server

Configuration

LSP Initialization Options

As part of the Initialize message within initializationOptions?: LSPAny; we support the following settings:

{
  "activateVulnmapOpenSource": "true",
  // Enables Vulnmap Open Source - defaults to true
  "activateVulnmapCode": "false",
  // Enables Vulnmap Code, if enabled for your organization - defaults to false, deprecated in favor of specific Vulnmap Code analysis types
  "activateVulnmapIac": "true",
  // Enables Infrastructure as Code - defaults to true
  "insecure": "false",
  // Allows custom CAs (Certification Authorities)
  "endpoint": "https://example.com",
  // Vulnmap API Endpoint required for non-default multi-tenant and single-tenant setups
  "additionalParams": "--all-projects",
  // Any extra params for Open Source scans using the Vulnmap CLI, separated by spaces
  "additionalEnv": "MAVEN_OPTS=-Djava.awt.headless=true;FOO=BAR",
  // Additional environment variables, separated by semicolons
  "path": "/usr/local/bin",
  // Adds to the system path used by the CLI
  "sendErrorReports": "true",
  // Whether to report errors to Vulnmap - defaults to true
  "organization": "a string",
  // The name of your organization, e.g. the output of: curl -H "Authorization: token $(vulnmap config get api)"  https://vulnmap.khulnasoft.com/api/cli-config/settings/sast | jq .org
  "enableTelemetry": "true",
  // Whether user analytics can be tracked
  "manageBinariesAutomatically": "true",
  // Whether CLI/LS binaries will be downloaded & updated automatically
  "cliPath": "/a/patch/vulnmap-cli",
  // The path where the CLI can be found, or where it should be downloaded to
  "token": "secret-token",
  // The Vulnmap token, e.g.: vulnmap config get api or a token from oauth flow
  "automaticAuthentication": "true",
  // Whether LS will automatically authenticate on scan start (default: true)
  "enableTrustedFoldersFeature": "true",
  // Whether LS will prompt to trust a folder (default: true)
  "trustedFolders": [
    "/a/trusted/path",
    "/another/trusted/path"
  ],
  // An array of folder that should be trusted
  "activateVulnmapCodeSecurity": "false",
  // Enables Vulnmap Code Security reporting
  "activateVulnmapCodeQuality": "false",
  // Enable Vulnmap Code Quality issue reporting (Beta, only in IDEs and LS)
  "deviceId": "a UUID",
  // A unique ID from the running the LS, used for telemetry
  "integrationName": "ECLIPSE",
  // The name of the IDE or editor the LS is running in
  "integrationVersion": "1.0.0",
  // The version of the IDE or editor the LS is running in
  "filterSeverity": {
    // Filters to be applied for the determined issues
    "critical": true,
    "high": true,
    "medium": true,
    "low": true,
  },
  "scanningMode": "auto",
  // Specifies the mode for scans: "auto" for background scans or "manual" for scans on command
  "authenticationMethod": "token",
  // Specifies the authentication method to use: "token" for Vulnmap API token or "oauth" for Vulnmap OAuth flow. Default is token.
  "vulnmapCodeApi": "https://deeproxy.vulnmap.khulnasoft.com",
  // Specifies the Vulnmap Code API endpoint to use. Default is https://deeproxy.vulnmap.khulnasoft.com
}

activateVulnmapCode automatically toggles the value of activateVulnmapCodeSecurity and activateVulnmapCodeQuality. Therefore, to enable only one of the two analysis types, activateVulnmapCode must be removed from Initialization Options for the specific analysis type option to have an effect.

Workspace Trust

As part of examining the codebase for vulnerabilities, Vulnmap may automatically execute code on your computer to obtain additional data for analysis. For example, this includes invoking the package manager (e.g., pip, gradle, maven, yarn, npm, etc.) to get dependency information for Vulnmap Open Source. Invoking these programs on untrusted code that has malicious configurations may expose your system to malicious code execution and exploits.

To safeguard from using the language server on untrusted folders, our language server will ask for folder trust before running scans against these folders. When in doubt, do not grant trust.

The trust feature is enabled by default. When a folder is trusted, all sub-folders are also trusted. After a folder is trusted, Vulnmap Language Server notifies the Language Server Client with the custom $/vulnmap.addTrustedFolders notification, which contains a list of currently trusted folder paths. Based on this, a client can then implement logic to intercept this notification and persist the decision and trust in the IDE or Editor storage mechanism.

Trust dialogs can be disabled by setting enableTrustedFoldersFeature to false in the initialization options. This will disable all trust prompts and checks.

An initial set of trusted folders can be provided by setting trustedFolders to an array of paths in the initializationOptions. These folders will be trusted on startup and will not prompt the user to trust them.

Environment variables

Vulnmap LS and Vulnmap CLI support and need certain environment variables to function:

1. HTTP_PROXY, HTTPS_PROXY and NO_PROXY to define the http proxy to be used
2. JAVA_HOME to analyse Java JVM-based projects via Vulnmap CLI
3. PATH to find maven when analysing Maven projects, to find python, etc

Auto-Configuration

To automatically add these variables to the environment, Vulnmap LS searches for the following files, with the order determining precedence. If the executable is not called from an already configured environment (e.g. via zsh -i -c 'vulnmap-ls'), you can also specify config file with the -c command line flag for setting the above mentioned variables. Vulnmap LS reads the following files in the given precedence and order, not overwriting the already loaded variables.

given config file via -c flag
<working-dir>/.vulnmap.env
$HOME/.vulnmap.env

Any lines that contain an environment variable in the format VARIABLENAME=VARIABLEVALUE are added automatically to the environment if not already existent. This adheres to the dotenv format. In case of .profile, .zshrc, etc., if a variable is directly exported e.g. via export VARIABLENAME=VARIABLEVALUE, it is not loaded. The export would need to be split of and be in its own line, e.g

VARIABLENAME=VARIABLEVALUE
export VARIABLENAME

The PATH variable is treated differently than all other variables, as it is an aggregate of all PATH variables found in the files and in the environment. Also, the current working directory . is automatically added to the path, so a download of the Vulnmap CLI into the current working directory by an LSP client would yield a found Vulnmap CLI for the Language Server.

In addition to configuring variables via config files, Vulnmap LS adds the following directories to the path on linux and macOS:

• /bin
• $HOME/bin
• /usr/local/bin
• $JAVA_HOME/bin

If no JAVA_HOME is set, it automatically searches for a java executable first in path, then in the following directories and adds the parent directory of its parent as JAVA_HOME. The following directories are recursively searched:

• /usr/lib
• /usr/java
• /opt
• /Library
• $HOME/.sdkman
• C:\Program Files
• C:\Program Files (x86)

The same directories are searched for a maven executable and the parent directory is added to the path.

Vulnmap CLI

To find the automatically managed Vulnmap CLI, the XDG Data Home and PATH path are automatically scanned for the OS-dependent file, e.g. vulnmap-macos on macOS, vulnmap-linux on Linux and vulnmap-win.exe on Windows, and the first path where it is found is added to the environment. It is later used for all functionality that depends on the CLI.

Setting environment variables globally

If you want to have the environment variables available system-wide, you would need to add the variables to /etc/environment or on macOS to /etc/launchd.conf or set them via launchctl in a shell script. The former two locations are automatically read by vulnmap lsp. On Windows, a user variable can be defined via the UI for the user or system-wide. In a file like ~/.profile it would like this:

VULNMAP_TOKEN=<your-token-from-app.vulnmap.khulnasoft.com>
DEEPROXY_API_URL=https://deeproxy.vulnmap.khulnasoft.com/

# export variables, but make sure the export is not on the same line as the variable definition
export VULNMAP_TOKEN
export DEEPROXY_API_URL

Authentication to Vulnmap

The Vulnmap LS authentication flow happens automatically, unless disabled in configuration, and is as follows. When Vulnmap Language Server starts, it:

• If the endpoint is a vulnmapgov.io endpoint, or the authenticationMethod is set to oauth, it authenticates via OAuth2. This opens a browser window.
• If the authentication method is not oauth, it tries to retrieve a token using the Vulnmap CLI token authentication.
• If the CLI is not authenticated either, it opens a browser window to authenticate
• If there are problems opening the browser window, the auth URL can be copied to the clipboard (via implementation of vulnmap.copyAuthLink). Note that there is a requirement to have xsel or xclip installed for Linux/Unix users for this feature.

After successfull authentication in the web browser, the Vulnmap Language Server automatically retrieves the Vulnmap authentication credentials and uses them for further requests.

Run Tests

go test ./...

If you have any issues with running pact, please extend your PATH env. For example:

PATH=$PATH:$PWD/.bin/pact/bin make test

The output should look like this (it is running against the Vulnmap Code API and using the real CLI):

?       github.com/khulnasoft-lab/vulnmap-ls        [no test files]
ok      github.com/khulnasoft-lab/vulnmap-ls/code   24.201s
ok      github.com/khulnasoft-lab/vulnmap-ls/diagnostics    26.590s
ok      github.com/khulnasoft-lab/vulnmap-ls/iac    25.780s
?       github.com/khulnasoft-lab/vulnmap-ls/lsp    [no test files]
ok      github.com/khulnasoft-lab/vulnmap-ls/oss    22.427s
ok      github.com/khulnasoft-lab/vulnmap-ls/server 48.558s
ok      github.com/khulnasoft-lab/vulnmap-ls/util   9.562s

Test Github Action locally

You can test github actions locally using act.

Install act & prerequisites

brew install act

# if you don't have docker desktop you can use minikube (a one-node kubernetes distribution)
brew install --cask virtualbox # you need to enable the virtualbox extension in macOS settings
brew install minikube
minikube start
eval $(minikube docker-env) # gives you a fully functional docker environment

Run act

act --secret VULNMAP_TOKEN=$VULNMAP_TOKEN --secret DEEPROXY_API_URL=$DEEPROXY_API_URL